Exchange Security Insights Online Collector (Azure Monitor)

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index


Attribute Value
Connector ID ESI-ModernExchangeOnlineCollector
Publisher Microsoft
Used in Solutions Microsoft Exchange Security - Exchange Online
Collection Method CCF Push
Connector Definition Files ESI-ModernExchangeOnlineCollector_connectorDefinition.json
DCR Definition Files ESI-ModernExchangeOnlineCollector_DCR.json
CCF Configuration ESI-ModernExchangeOnlineCollector_dataConnector.json
CCF Capabilities Push
Ingestion API Log Ingestion API — CCF Push connectors use DCR-based Log Ingestion API
Custom Log V1 Tables Yes 🔶 — ingests into tables with type-suffixed columns
Microsoft Learn View on Learn

Connector used to push Exchange Online Security configuration for Microsoft Sentinel Analysis using Azure Monitor Ingestion API.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
ESIAPIExchangeOnlineConfig_CL 🔶 ? ✓ ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions:

Custom Permissions:

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE - UPDATE

ℹ️

NOTE - UPDATE:

For an existing deployment, update the collector script to version 8.0.0.0 or later, before switching to the Azure Monitor Log Ingestion API.
See ESI On-Premises Collector Update and Upgrade an existing deployment.
For detailed documentation for the following steps, refer to the Official Documentation

1. STEP 1. Deploy the Azure Monitor connector resources

This connector enables the Exchange Online collector to send configuration data to Microsoft Sentinel through the Azure Monitor Log Ingestion API.

Automated Azure Monitor resource deployment

Selecting Deploy creates the Log Analytics table, Data Collection Endpoint (DCE), and Data Collection Rule (DCR). The Azure Automation deployment in the next step creates a system-assigned managed identity and grants it access to the DCR. Deploy Exchange Collector Push connector resources

STEP 2 - Deploy / Updating the Azure Automation collector

IMPORTANT: Before deploying Azure Automation, record the values below. For new deployment, choose your environment display name (this name will be used in the workbooks - remember the table can contain information from several environments), for example Contoso. The deployment adds the -Cloud suffix when needed.

Option 1 : Deploy the Azure Automation template for a new deployment

  1. Select the Deploy to Azure button below.

    Deploy To Azure

  2. Check the subscription, Select the resource group, Check the location.

  3. Enter the Automation account name, environment name, tenant ID, DCE URI, DCR immutable ID, and DCR name. To retrieve the DCR name, follow Retrieve the DCR name.

  4. Select Review + create, and then select Create.

The template creates the Automation account with a system-assigned managed identity, imports the required modules, deploys the runbook and daily schedule, creates the configuration variables, and assigns the managed identity to the DCR.

Option 2 : Update an existing Deployment of Azure Automation

Use the following documentation to update an existing Azure Automation deployment. Click Here

STEP 3 - Assign Microsoft Graph and Exchange Online permissions to the managed identity (only for new deployment)

The Automation account managed identity requires application permissions to collect Exchange Online and Microsoft Graph information. Assign Permissions by Script

A. Download Permission Script

From a secure machine with the Microsoft Graph modules installed, download the Permission Update script.

(The script is also located in the CollectExchSecIns.zip file, so if the On-Premises solution is already deployed this modification can be done on this server.)

Permission Update script

B. Retrieve the Azure Automation managed identity object ID

Open the Automation account, select Identity, and copy the managed identity object ID.

C. Unblock the script and run the script with a Global Administrator account

Run ExchangeOnlinePermSetup.ps1 -MIIDParam <managed-identity-object-id> -TenantId <tenant-id> -InteractiveAuth. The script requires Microsoft Graph modules and admin consent. It assigns Exchange.ManageAsApp, User.Read.All, Group.Read.All, and AuditLog.Read.All.

D. Exchange Online Role Assignment. Do not forget this step !

  1. As a Global Administrator, go to Roles and Administrators.
  2. Select Global Reader role or Security Reader and click to 'Add assignments'.
  3. Click on 'No member selected' and search your Managed Identity account Name beginning by the name of your automation account like 'ESI-Collector'. Select it and click on 'Select'.
  4. Click Next and validate the assignment by clicking Assign.

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · Logic Apps · 📊

↑ Back to Connectors Index